Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@app/app.vue`:
- Around line 131-141: The top-level if using isBlogPostRoute.value runs only
once at setup so OG image won't update on client-side navigations; change this
to a reactive effect (e.g. use watchEffect or watch(isBlogPostRoute)) that
re-evaluates when route.path/isBlogPostRoute changes and calls defineOgImage
accordingly, or move the defineOgImage call into page-level components so each
page sets its own OG image; ensure you reference the existing isBlogPostRoute
computed and call defineOgImage inside the reactive watcher (and handle/clear
previous OG image if defineOgImage cannot be called multiple times).

In `@app/components/global/BlueskyPostEmbed.client.vue`:
- Around line 198-199: The template is incorrectly binding
post.embed.aspectRatio.width/height to the height and width attributes (creating
tiny pixel dimensions); remove the :height and :width bindings for the embed
element and instead apply a style using CSS aspect-ratio derived from
post.embed.aspectRatio (e.g., set :style to an object like { aspectRatio:
`${post.embed.aspectRatio.width}/${post.embed.aspectRatio.height}` } when
post.embed.aspectRatio exists), mirroring the existing pattern used for
img.aspectRatio elsewhere in BlueskyPostEmbed.client.vue so the embed scales
correctly.

---

Outside diff comments:
In `@app/components/global/BlueskyPostEmbed.client.vue`:
- Line 91: The code returns response.posts[0] without ensuring posts has
elements; update the logic that returns the post (the expression using
response.posts[0] in BlueskyPostEmbed.client.vue) to first check that
response.posts is an array and has length > 0 (e.g.,
Array.isArray(response.posts) && response.posts.length > 0) then return
response.posts[0], otherwise return null; ensure you use the same variable names
(response and posts) so type-checkers and callers remain correct.